Repository navigation
Overrides: zod, glob and minimatch past their advisories - #51
Merged
Merged
Conversation
node-forge (#46), source-map-js (#47), uuid (#48, through @expo/config-plugins 57.0.11) and shell-quote (#50) were fixed by ordinary updates. These three are dependencies of Expo whose fix is a major its parent's range does not allow, so they are forced with npm overrides: - zod ^4.6.6 (high; @expo/cli, which uses only z.object, string, enum, union, literal, safeParse and error.issues — all in zod 4) - glob ^14.0.2 and minimatch ^11.0.1 (medium; @expo/cli, config, config-plugins, fingerprint, metro-config. glob 14 needs minimatch 11, so they move together) Checked: tsc --noEmit; every member Expo calls still exported (glob, globSync, globStream, sync, Minimatch, minimatch); expo config; @expo/fingerprint; expo export for Android and iOS; expo start serving Metro, and Expo's dev-tools plugin schema accepting and rejecting under zod 4. Lockfile written with npm 10. Left open: deepmerge and one node-forge advisory have no fixed release.
lana-20
force-pushed
the
dependency-overrides
branch
from
November 3, 2026 16:38
c0206c3 to
c8aa352
Compare
lana-20
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
node-forge (#46), source-map-js (#47), uuid (#48, through
@expo/config-plugins 57.0.11) and shell-quote (#50) were fixed by
ordinary updates. These three are dependencies of Expo whose fix is a
major its parent's range does not allow, so they are forced with npm
overrides:
enum, union, literal, safeParse and error.issues — all in zod 4)
config-plugins, fingerprint, metro-config. glob 14 needs minimatch
11, so they move together)
Checked: tsc --noEmit; every member Expo calls still exported (glob,
globSync, globStream, sync, Minimatch, minimatch); expo config;
@expo/fingerprint; expo export for Android and iOS; expo start serving
Metro, and Expo's dev-tools plugin schema accepting and rejecting under
zod 4. Lockfile written with npm 10.
Left open: deepmerge and one node-forge advisory have no fixed release.